Click any tag below to further narrow down your results
Links
@wulfie_bain_ on X
An OpenAI Startups applied AI lead argues that prompts in even the best AI companies grow contradictory over time because teams only add lines and never remove them. He proposes treating prompts like code and product decisions, using a modular, MECE structure (Background, Behaviour, Output).
- Prompts evolve accretively, so contradictions and ambiguity pile up. Conditional prompts spread across files make the whole thing hard for anyone to review end to end.
- He reports results from prompt rewrites: one startup cut agent speed-ups of about 50%, another saw 40% higher 7-day retention, and another cut costs by 30%.
- Smarter models don't fix ambiguity. Someone still has to specify what the product should do, and evals force that clarity.
@eng_khairallah1 on X
A post claims that a file Andrej Karpathy reportedly uses, called LOOPS.md, transformed the author's Claude setup, making responses feel tailored to how they think. The author's pitch is to build a system that drives the model rather than prompting it turn by turn.
- The author says a friend on Karpathy's team at Anthropic shared the LOOPS.md file he actually uses, five weeks after he joined.
- After adding the file to their setup, the author reports Claude's first response was "completely different" and matched their working style.
- The core takeaway is that users should build a persistent system around the model instead of talking to it directly.